The client nexus is a cached version of the
server nexus for a particular
user. This client nexus is created when a user logs in. Login authentication must handled externally to Jetfire.
The client nexus contains a cache workflow objects and workflow classes that are accessible by a particular user. The cache may contain all the workflow objects and workflow classes accessible by a particular user or a subset (see
workspace for creating subsets).
Client nexus responsibilities:
- Providing a cache of workflow objects and classes for an individual user for use by the application interface.
- Workflows(objects) will not be cached if the workflow's roles do not match one of the user's roles.
- Workflows within a workspace will not be cached if the workspace's roles do not match one of the user's roles.
- If the workflow(object) has no roles and the above workspace restriction does not apply then it will be cached.
- Maintaining a communication channel with the server nexus.
- Queuing requests (new, get, set and execute) from the application interface.
- Sending new and updated objects to the server nexus.
- Creating audit workflows describing application requests.
- Receiving new and updated objects that have been changed by other client nexuses from the server nexus.
See Also